Summary

Refactors the application architecture and fixes code quality issues across SecurityConfig, BankController, AccountService, and one minimal template fix, without changing endpoints or build tooling.

Changes

1. Constructor injection — Replaced all field @Autowired with constructor injection in SecurityConfig, BankController, and AccountService. Fields are now private final.

2. loadUserByUsername() cleanup — Removed the dead if (account == null) check (the preceding findAccountByUsername already throws on not-found). Now queries accountRepository directly and throws UsernameNotFoundException.

3. Proper exceptions — Replaced generic RuntimeException with ResponseStatusException:

   • NOT_FOUND for "Account not found" and "Recipient account not found"
   • CONFLICT for "Username already exists"
   • BAD_REQUEST for "Insufficient funds" and validation failures
   • Controller uses getReason() (not getMessage()) to extract clean error text for UI display

4. @Transactional — Added to deposit(), withdraw(), transferAmount(), and registerAccount() to ensure atomicity (especially transferAmount which does multiple DB writes).

5. Input validation — Deposit/withdraw/transfer amounts validated as positive (> 0). Username and password validated as non-blank during registration.

6. SecurityConfig simplification — Removed the legacy configureGlobal(AuthenticationManagerBuilder) method. Since AccountService implements UserDetailsService and is a @Service, Spring Security auto-discovers it. Removed the AccountService dependency from SecurityConfig entirely. Changed passwordEncoder() from static to instance method.

7. Consistent error handling in controller — Added try-catch to the deposit endpoint (was missing, unlike withdraw/transfer). Updated register template to use th:text="${error}" instead of hardcoded "User already present." so new validation errors display correctly.

Review & Testing Checklist for Human

• Verify login/logout still works — SecurityConfig no longer explicitly wires UserDetailsService; Spring auto-discovers it via AccountService @Service
• Test deposit, withdraw, and transfer with amount = 0 or negative to confirm validation rejects them
• Test registration with blank username/password to confirm validation displays correct error
• Test transfer atomicity — if recipient doesn't exist, sender balance should not change
• Verify error messages display cleanly on both dashboard and registration pages

Notes

• No changes to pom.xml or tests
• One minimal template change: register.html updated to show dynamic error messages (required to match new validation behavior)
• All REST endpoints and behavior preserved
• Compilation verified with ./mvnw clean compile -DskipTests

Link to Devin session: https://app.devin.ai/sessions/cb1fa0ebeb6f4536a023113b2ec924c6
Requested by: @Colhodm